Dynamic usage inequity detection and/or remedy

ABSTRACT

The described subject matter relates to an architecture that can dynamically detect and/or automatically remedy service usage inequities in a communications network. In particular, based upon a comparison of incoming call detail records (CDRs) to various subscriber information (e.g., service plan, blacklisted devices for the service plan, historic or current billing cycle usage, etc.), the architecture can identify when a usage inequity occurs or is likely to occur, substantially in real time.

TECHNICAL FIELD

The present application relates generally to communications networks,and more specifically to automatic or dynamic usage inequity detectionand/or remedy.

BACKGROUND

Conventional communications networks that provide network services forsubscribers based upon a contractual service agreement tend to providevarious service plans, but do not investigate to determine if theselected service plans are suitable for the subscribers.

For example, a subscriber might have agreed to a feature-rich serviceplan or one with a very large amount of minutes or other usageparameters, yet rarely use many of the available features or asignificant portion of the provisioned usage allocation. Conversely, thesubscriber might agree to a service plan that can be relativelyinexpensively provided by the network because the service plan is tiedto certain devices that are generally not capable of incurringsubstantial costs to the network through customary use. However, aftersuch service is ordered, the terms agreed to by the subscriber can beviolated, which can lead to substantial costs to the network. Forinstance, the subscriber can swap the subscriber identity module (SIM)from the provisioned device to an unauthorized one (or engage in devicetethering or the like) that can take advantage of the services providedin a manner not intended by the network, and thus undermine thefeasibility of low-cost service plans.

Currently, host networks do not have the ability to prevent suchbehavior after the ordering phase. In other words, the network providercan allocate service plans based upon devices identified during theordering of service by the subscriber, but have no ability to detect theusage inequities noted.

SUMMARY

The following presents a simplified summary of the disclosed subjectmatter in order to provide a basic understanding of some aspects of thedisclosed subject matter. This summary is not an extensive overview ofthe disclosed subject matter. It is intended to neither identify key orcritical elements of the disclosed subject matter nor delineate thescope of the disclosed subject matter. Its sole purpose is to presentsome concepts of the disclosed subject matter in a simplified form as aprelude to the more detailed description that is presented later.

The subject matter disclosed herein, in one aspect thereof, comprises anarchitecture that can facilitate dynamic detection as well as automaticremedy of service usage inequities in a communication network. Inaccordance therewith and to other related ends, the architecture caninclude an extraction component that can retrieve subscriber informationassociated with a subscriber to the communications network. Thesubscriber information can include one or more call detail record (CDR)associated with a communication transaction (e.g., voice or data) of thesubscriber. In one or more aspects, the subscriber information can alsoinclude various other data such as rules data or provision data thatincludes data relating to at least one of a provisioned serviceagreement agreed to by the subscriber, enabled features associated withthe service agreement, terms and conditions associated with the serviceagreement, other available service plans, historic usage for thesubscriber, current billing cycle usage for the subscriber and so forth.

The architecture can also include a detection component that can examinethe subscriber information. For example, the detection component cancompare data included in the CDR to other subscriber information.Regardless, based upon this examination, the detection component cangenerate a data usage event message when a usage inequity is identified.In one or more aspect, the usage inequity can relate to avoidable highdata usage charges deemed likely to arise during a billing cycle orotherwise. In these or other aspects, the usage inequity can also relateto the detection of a usage violation such as the detection of SIMswapping or device tethering or the like.

In one or more aspects, the architecture can also include a controlservice component that can receive the data usage event message, andthat can determine, based upon rules data, a suitable treatment to applyin connection with the subscriber, generally in a manner intended toremedy or mitigate the usage inequity. In one or more aspects, thesuitable treatment can relate to, e.g., transmitting a notification tothe subscriber, wherein the notification can include one or more of theusage inequity, suggested remedies, potential actions should the usageinequity continue, or further contact information; additional or moredetailed monitoring of data usages associated with the subscriber; arestriction to data usage or services associated with the subscriber; atermination of data usage or services associated with the subscriber,and so on.

The following description and the annexed drawings set forth in detailcertain illustrative aspects of the disclosed subject matter. Theseaspects are indicative, however, of but a few of the various ways inwhich the principles of the disclosed subject matter may be employed andthe disclosed subject matter is intended to include all such aspects andtheir equivalents. Other advantages and distinguishing features of thedisclosed subject matter will become apparent from the followingdetailed description of the disclosed subject matter when considered inconjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system that can facilitate automaticand/or dynamic detection and/or remedy of service usage inequities in atelecommunications network.

FIG. 2A provides a block diagram that depicts various example subscriberinformation 104.

FIG. 2B depicts a block diagram that illustrates exemplary usageinequities 110.

FIG. 3 illustrates a block diagram of a system that can determinesuitable actions in response to data usage event message processing.

FIG. 4 is a block diagram of various example treatment 304determinations.

FIG. 5 provides illustration 500 depicts an exemplary decision pathassociated with a particular SOC.

FIG. 6 illustrates a block diagram of a system that can perform or aidwith various determinations or inferences

FIG. 7 is an exemplary flow chart of procedures that define a method forautomatically or dynamically detecting or remedying service usageinequities for a communications network.

FIG. 8 is an exemplary flow chart of procedures that define a method forproviding various additional features or aspects in connection withidentifying a usage inequity or other Enabler functionality.

FIG. 9 depicts an exemplary flow chart of procedures defining a methodfor providing various addition features or aspects in connection withdetermining treatment or other DUCS functionality.

FIG. 10 illustrates an example wireless communication environment withassociated components that can enable operation of an enterprise networkin accordance with aspects described herein.

FIG. 11 illustrates a schematic deployment of a macro cell for wirelesscoverage in accordance with aspects of the subject specification.

FIG. 12 illustrates a block diagram of a computer operable to execute aportion of the disclosed architecture.

DETAILED DESCRIPTION

The disclosed subject matter is now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the disclosed subject matter. It may beevident, however, that the disclosed subject matter may be practicedwithout these specific details. In other instances, well-knownstructures and devices are shown in block diagram form in order tofacilitate describing the disclosed subject matter.

As used in this application, the terms “system,” “component,”“interface,” and the like are intended to refer to a computer-relatedentity or an entity related to an operational machine with one or morespecific functionalities. The entities disclosed herein can be eitherhardware, a combination of hardware and software, software, or softwarein execution. For example, a component may be, but is not limited tobeing, a process running on a processor, a processor, an object, anexecutable, a thread of execution, a program, and/or a computer. By wayof illustration, both an application running on a server and the servercan be a component. One or more components may reside within a processand/or thread of execution and a component may be localized on onecomputer and/or distributed between two or more computers. Thesecomponents also can execute from various computer readable media havingvarious data structures stored thereon. The components may communicatevia local and/or remote processes such as in accordance with a signalhaving one or more data packets (e.g., data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network such as the Internet with other systemsvia the signal). As another example, a component can be an apparatuswith specific functionality provided by mechanical parts operated byelectric or electronic circuitry that is operated by software orfirmware application(s) executed by a processor, wherein the processorcan be internal or external to the apparatus and executes at least apart of the software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components. An interface can include input/output (I/O)components as well as associated processor, application, and/or APIcomponents.

Furthermore, the disclosed subject matter may be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer to implement thedisclosed subject matter. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips . . . ), opticaldisks (e.g., compact disk (CD), digital versatile disk (DVD) . . . ),smart cards, and flash memory devices (e.g., card, stick, key drive . .. ). Additionally it should be appreciated that a carrier wave can beemployed to carry computer-readable electronic data such as those usedin transmitting and receiving electronic mail or in accessing a networksuch as the Internet or a local area network (LAN). Of course, thoseskilled in the art will recognize many modifications may be made to thisconfiguration without departing from the scope or spirit of thedisclosed subject matter.

As used herein, the terms “infer” or “inference” generally refer to theprocess of reasoning about or inferring states of the system,environment, and/or user from a set of observations as captured viaevents and/or data. Inference can be employed to identify a specificcontext or action, or can generate a probability distribution overstates, for example. The inference can be probabilistic—that is, thecomputation of a probability distribution over states of interest basedon a consideration of data and events. Inference can also refer totechniques employed for composing higher-level events from a set ofevents and/or data. Such inference results in the construction of newevents or actions from a set of observed events and/or stored eventdata, whether or not the events are correlated in close temporalproximity, and whether the events and data come from one or severalevent and data sources.

Further, terms like “user equipment,” “mobile station,” “mobile,”subscriber station,” “access terminal,” “terminal,” “handset,” andsimilar terminology, generally refer to a wireless device utilized by asubscriber or user of a wireless communication service to receive orconvey data, control, voice, video, sound, gaming, or substantially anydata-stream or signaling-stream. The foregoing terms are utilizedinterchangeably in the subject specification and related drawings.Likewise, the terms “access point,” “base station,” “cell site,” and thelike, are utilized interchangeably in the subject application, and referto a wireless network component or appliance that serves and receivesdata, control, voice, video, sound, gaming, or substantially anydata-stream or signaling-stream from a set of subscriber stations. Dataand signaling streams can be packetized or frame-based flows. It isnoted that in the subject specification and drawings, context orexplicit distinction provides differentiation with respect to accesspoints or base stations that serve and receive data from a mobile devicein an outdoor environment, and access points or base stations thatoperate in a confined, primarily indoor environment overlaid in anoutdoor coverage area. Data and signaling streams can be packetized orframe-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,” andthe like are employed interchangeably throughout the subjectspecification, unless context warrants particular distinction(s) amongthe terms. It should be appreciated that such terms can refer to humanentities, associated devices, or automated components supported throughartificial intelligence (e.g., a capacity to make inference based oncomplex mathematical formalisms) which can provide simulated vision,sound recognition and so forth. In addition, the terms “wirelessnetwork” and “network” are used interchangeable in the subjectapplication, when context wherein the term is utilized warrantsdistinction for clarity purposes such distinction is made explicit.

Moreover, the word “exemplary” is used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to present concepts in a concrete fashion. As usedin this application, the term “or” is intended to mean an inclusive “or”rather than an exclusive “or”. That is, unless specified otherwise, orclear from context, “X employs A or B” is intended to mean any of thenatural inclusive permutations. That is, if X employs A; X employs B; orX employs both A and B, then “X employs A or B” is satisfied under anyof the foregoing instances. In addition, the articles “a” and “an” asused in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or clear fromcontext to be directed to a singular form.

Referring now to the drawing, with reference initially to FIG. 1, system100 that can facilitate automatic and/or dynamic detection and/or remedyof service usage inequities in a telecommunications network is depicted.Generally, system 100 can include extraction component 102 that canretrieve subscriber information 104 associated with one or moresubscribers to a telecommunication network. Typically, thecommunications network will be a wireless communication network, but itshould be appreciated that the disclosed subject matter can also applyto substantially any type of telecommunications network. Subscriberinformation 104 can optionally include a variety of data or data sets,which is further detailed infra in connection with FIG. 2A. However,subscriber information 104 will normally include at least one or morecall detail record (CDR) 106 associated with a communication-basedtransaction of the subscriber, such as a call, text, download, orsubstantially any other voice or data transaction.

CDRs (e.g., CDR 106) are typically produced automatically for a call orother transaction types, and typically include a source identifier(e.g., number or ID of the calling device), a destination identifier(e.g., number or ID of a called device), a time stamp, a duration, atransaction type (e.g., voice or data), and so forth. CDRs can thus bestored or archived by the host communications network or an agent orpartner thereof, such as to data store 114. Accordingly, extractioncomponent 102 can retrieve CDR 106 from data store 114 or from othernetwork components. For example, in one or more aspects of the disclosedsubject matter, extraction component 102 can retrieve CDR 106 from aGeneral Packet Radio Service (GPRS) Serving Support Node (SGSN)associated with the communications network. Hence, extraction component102 can retrieve CDRs as they are created or received by particularnetwork equipment, devices or components; or retrieve CDRs from datastore 114.

Data store 114 is intended to be a repository of all or portions ofdata, data sets, or information described herein or otherwise suitablefor use with the described subject matter. Data store 114 can becentralized, either remotely or locally cached, or distributed,potentially across multiple devices and/or schemas. Furthermore, datastore 114 can be embodied as substantially any type of memory, includingbut not limited to volatile or non-volatile, sequential access,structured access, or random access and so on. It should be understoodthat all or portions of data store 114 can be included in system 100, orcan reside in part or entirely remotely from system 100.

Furthermore, system 100 can include detection component 108 that canexamine subscriber information 104. Based upon the examination ofsubscriber information 104, detection component 108 can identify usageinequity 110, which is discussed in more detail with reference to FIG.2B. Accordingly, when a usage inequity 110 is identified, detectioncomponent 108 can also generate data usage event message 112. Thus, datausage event message 112 can alert as well as describe one or more usageinequity 110 that can be derived from CDR 106 as well as from othersubscription information 104, which can now be described.

While still referring to FIG. 1, but turning now also to FIGS. 2A and2B, FIG. 2A depicts various example subscriber information 104, whileFIG. 2B illustrates exemplary usage inequities 110. Referringspecifically to FIG. 2A, as already mentioned, subscriber information104 can be or can include CDR 106, which is intended to refer to aeither a single CDR 106 or a collection or history of CDRs 106, such asthose within a current or past billing cycle. Other examples ofsubscriber information 104 can include various provision data (denotedby reference numerals 204-210) that can be retrieved from an accountsdata store (which can be included in or separate from data store 114)associated with the communications network, and rules data 212, which isfurther described in connection with FIG. 3.

Thus, while rules data 212 can be included in subscriber information104, detection component 108 will commonly focus on comparisons betweenCDR 106 and provision data 204-210 in order to identify usage inequity110. By way of illustration, provision data can relate to a serviceagreement and/or terms and conditions of a service agreement between thenetwork and a network subscriber, which is denoted by reference numeral204. Similarly, the provision data can relate to other serviceagreements such as those associated with disparate subscribers and/or toother available service plans, which is labeled by reference numeral206. In addition, provision data can include various features, options,or service order codes (SOC) associated with the service agreement ofthe subscriber; or those features, options, or SOCs otherwise availableor provided by the network, which are denoted by reference numerals 208and 210, respectively.

Continuing on to FIG. 2B, one example of usage inequity 110 can be anavoidable high data usage charge, for instance, one that is deemed(e.g., inferred or determined) likely to arise during a billing cycle orotherwise, which is depicted by reference numeral 220. Another exampleusage inequity 110 can relate to usage that is more suitable for adisparate service or features thereof, labeled as reference numeral 222.For example, usage by the subscriber that consistent falls short of acurrent associated service plan or features thereof, or thatconsistently falls below a less expensive service plan can give rise tousage inequity 110. Such usage inequities 110, once identified, can beprocessed (discussed with reference to FIG. 3) and employed toproactively suggest a means for the subscriber to reduce costsassociated with his or her current service plan.

Conversely, usage inequities 110 can also be identified when such relateto usage violations 224 in which usage of the communications networkviolates a provisioned service agreement or rate plan agreed to by thesubscriber. Examples of usage violation 224 (and/or usage inequity 110)can be, e.g., a subscriber identity module (SIM) swap 226 or devicetether 228. SIM swap 226 can occur, e.g., when a SIM for one device isswitched with that for a second device, typically a second device thathas a richer feature set. Likewise, device tether 228 can occur, e.g.,when a first device is communicatively tethered to a second device,typically one with a richer feature set in order to employ the networkprovided by the first device. Both cases can result in a violation ofthe terms and conditions of a provisioned service and/or the serviceagreement agreed to by the subscriber, and can thus be identified asusage inequity 110.

Still referring to FIG. 1, detection component 108 can identifyavoidable high data usage charges 220 by forecasting usage relative toan amount of time remaining in a billing cycle or by identifying usageby the subscriber that surpasses a respective threshold at one or moreperiods of the billing cycle. As for occurrences that can constituteusage violations 224, detection component 108 can convert anInternational Mobile Equipment Identify (IMEI) included in CDR 106 intoan IMEI type. With this IMEI type, detection component 108 can then beappraised of the particular type or class of equipment employed for thecommunication transaction. Hence, this IMEI type can be compared to IMEItype or types of authorized or allowable equipment included insubscriber information 104 (e.g., provision data) or to IMEI type(s)included in a blacklist equipment list, also potentially included insubscriber information 104, that specifically enumerates equipment ordevices that are prohibited from use with the subscriber's serviceagreement or rate plan.

It should be appreciated that usage inequity 110 can be identifiedsubstantially in real time. For example, usage inequity 110 can beidentified contemporaneously with a communication transaction and/orwith the creation of an associated CDR 106. In some cases, however, itcan be beneficial to delay the examination or determinations of usageinequities 110, but even in such cases, determinations can be madewithin a 24-hour period. Regardless, such determinations or inferencesassociated with usage inequities 110 can be identified dynamically,without action or supervision by human actors. Moreover, it should befurther appreciated that references herein to “Enabler rating engine,”“Enabler system,” or similar are generally intended to relate to system100 or components or features thereof.

Turning now to FIG. 3, system 300 that can determine suitable actions inresponse to data usage event message processing is illustrated. Inparticular, system 300 can include control service component 302 thatcan receive data usage event message 112. Control service component 302can process data usage event message 112 in connection with rules data212 in order to determine or infer suitable treatment 304 to apply withrespect to the subscriber (e.g., the subscriber associated with the oneor more CDRs 106 that resulted in issuance of data usage event message112 detailed supra). Control service component 302 can determine orinfer a variety of possible treatments, which is further detailed withreference to FIG. 4.

While still referring to FIG. 3, but turning now also to FIG. 4, variousexample treatment 304 determinations are depicted. Initially, a firstexample of treatment 304 can be notification 306, illustrated here aswell as in FIG. 3. Notification 306 can be issued by control servicecomponent 302 or by another component at the behest of control servicecomponent 302. Notification component 306 can be delivered to thesubscriber and can include details relating to usage inequity 110 as anyor all of the following or other suitable data: (1) a suggested remedyfor usage inequity 110 (e.g., switching service plans, adding/removingassociated features or options to provide a cost-benefit to thesubscriber); (2) potential actions should conditions associated withusage inequity 110 continue (e.g., in the case of usage violations,notification of further monitoring 402, a restriction 404 or atermination 406 of service); (3) or further contact information (e.g.,web or email addresses or phone numbers for customer care or the like).

Reference numeral 402 can indicate a determination by control servicecomponent 302 that additional or more detailed monitoring of data usagesassociated with the subscriber should be facilitated. On the other hand,usage restriction 404 can indicate control service component 302 hasdeemed it suitable to restrict data usage or services associated withthe subscriber, while usage termination 406 indicates a determinationthat it is suitable to terminate data usage or services associated withthe subscriber. It should be appreciated that while control servicecomponent 302 can determine treatment 304 such as further monitoring 402of subscriber usage, or a restriction 404 or a termination 406 ofservice is appropriate in a particular case, any or all of which can bereferred to in notification 306, the determination of whether or not tosend notification 306 at all can also be made as well. Hence, creationand/or propagation of notification 306 also represent treatment 304 thatcan be determined or inferred by control service component 302.

For instance, even if control service component 302 determines any oneof items 402-406 represent suitable treatment 304, notification 306 canbe first selected notifying the subscriber of the possibility that suchwill apply in order to allow the subscriber to amend his or her behaviorand/or violation of service terms and conditions. As another example,certain rules data 212 need not be applied automatically, even whenprocessed. Thus, instead of taking particular actions immediately(sending notification 306 or applying other treatment 304), the rulesdata 212 can be tested for a time during a provisional period wherein anaudit trail can be created to measure the effects (e.g., savings if theusage violation is corrected) of treatment 304 defined by a particularrule in rules data 212.

Still referring to FIG. 3, in one or more aspects of the disclosedsubject matter, notification 406 can be transmitted to the subscriber byway of short message service (SMS), email, or regular, physical mail.While particularly convenient in the cases of SMS or email, butultimately regardless of the method of delivery, control servicecomponent 302 can receive response 310 to notification 306. Response 310can be particularly relevant to the cases in which usage inequity 110relates to potential high usage charges or underutilization (e.g.,reference numerals 220 and 222 of FIG. 2B). For example, consider thesituation in which high usage costs are deemed likely within a billingcycle. Notification 306 can indicate this possibility as detailed supra,yet also identify a suitable service plan or feature or SOC that canaccommodate the high data usage in a manner that can save the subscribermoney. Similarly, in the situation of underutilization 222, notification306 can alert the user (potentially based upon examination of thecurrent and historic usage patterns) that a different service plan,e.g., one that carries a lower cost is suitable.

In either situation, the subscriber can be economically benefited,either by upgrading to a service plan or a SOC/features that avoidslikely overages or by downgrading to a cheaper plan that still coversthe subscriber's consistent usage patter. Hence, in either situation,notification 306 can indicate that the subscriber should modify acurrent service plan, which can be accomplished by agreement included inresponse 310. Thus, control service component 302 can automaticallyfacilitate update 312 to a provisioned service agreement or associatedfeatures when the subscribers authorizes update 312 or when thesubscriber requests an exemption in response to notification 306.

In addition, system 300 can also include interface component 308 thatcan enable authorized administrators to create or update rules data 212.As noted, rules data 212 can define how control service component 302interprets data usage event message 112, whether or not to generatenotification 306 or select other suitable treatment 304, and/or whetheror not to apply treatment 304 or forego that treatment, e.g., in favorof facilitating an audit trail. Moreover, as indicated by the header,system 300 or components or features thereof can be referred to as“DUCS” or a “Data Usage Control” System or Service or similar. Anexample decision tree is provided in connection with FIG. 5 to indicatean exemplary processing of subscriber information 104 and determinationof treatment 304.

However, before turning to FIG. 5, with the foregoing in mind, it shouldbe readily apparent that the features detailed herein can, inter alia,provide a mechanism for proactively detecting avoidable high data usagecosts during a billing cycle as well as service plan underutilization.In addition, the disclosed subject matter can also provide a mechanismfor communications networks to ensure a subscriber is abiding by theterms and conditions agreed to in a service agreement, or to identifyand react appropriately when such is not the case. Appreciably, ineither case, the subscriber can be notified of any identified usageinequity (e.g., usage inequity 110), which can potentially be identifieddynamically in substantially real time. Moreover, subscribers can beprovided the ability to automatically update features or options orservice agreements in response to the notification (e.g., notification306) relating to the usage inequity or inequities identified.

Accordingly, disclosed subject matter can provide the capability todetect the nature of the equipment a subscriber is utilizing, comparethat equipment type to the provisioned type, rate plan, features, rules,etc., and decide systematically whether to apply treatment (e.g.,treatment 304) of some type, generally predefined. In more detail, theEnabler ratings engine (e.g., system 100 or components or featuresthereof) can pull the IMEI from a Call Detail Records (e.g., CDR 106)arriving from the network SGSNs, which can then be translated to anassociated IMEI Type or class of equipment. Enabler can then compare theIMEI Type against the provisioned rate plan, features, and rules datasuch that if no match is found (or a match is found when comparing to anequipment blacklist), Enabler can compose an event (e.g., data usageevent message 112) for use by DUCS (e.g., system 300 or associatedcomponents or features) for determining suitable treatment.

Likewise, DUCS can allow a certified administrator, governance council,rules board, or substantially any eligible body to author and promulgatevarious rules (e.g., rules data 212) that guide determining treatment304. Such rules data 212 can be vetted and updated or promulgated in aconsistent way, for example, uploaded nightly to be used by the billingsystem data rating engine, Enabler, as incoming data CDRs are rated.DUCS can receive event messages from Enabler that represent a detectedrule violation or other usage inequity. The data payload of the messagecan contain the required data DUCS needs to properly evaluate the usageinequity and the treatment it might apply to the subscriber as a result.Appreciably, rules can enforce negative or positive treatment for anyparty, depending upon the particular scenario. For example, thecommunications network can choose to proactively guide a subscriber to alower cost feature or it may penalize a subscriber for SIM swapping to amore capable device such as a laptop.

DUCS can notify the subscriber by way of SMS, email, or postcard,wherein the notification can include various types of information aboutthe usage inequity. In addition, DUCS can also collect the affirmativeresponse (e.g., response 310) such as a reply SMS, authorizing DUCS toupgrade or otherwise modify the subscriber's data service. In extremecases of violations, DUCS can maintain the ability to shut off asubscriber's data capability entirely, or to restrict all or certainportions. Moreover, DUCS can also support a subscriber's request for arule exemption. In some aspects, DUCS can permit a “soak” period and/ora provisional period, during which no treatment need be applied, but onein which an audit trail can be created that measures the impact of therule if applied. Hence, effects of treatment can be inferred prior toimplementation and the communications network can deliver rules data andtreatment into production in relatively short period of time, such as,e.g., a week or two.

Accordingly, by employing the disclosed subject matter, numerousbenefits can be provided for the subscriber as well as the hostcommunications network. Such benefits can include: (1) an ability towarn subscribers of possible overage charges or underutilization; (2) anability for the host network to detect subscribers who violate theiraccepted terms and conditions by SIM swapping to higher capable datadevices; (3) an ability for the host network to detect subscribers whoviolate their accepted terms and conditions by tethering to highercapable data devices; (4) an ability for the host network to ensure thatsubscribers whose device types require specific provisioned features areactually provisioned with those features; (5) the ability for the hostnetwork to provide an exemption path for any subscriber to opt out ofthe automated treatment; (6) a simplification for marketing or otherdepartments to deploy vetted rules into production with expedience; (7)an ability for subscribers to avoid high pay-per-use data usage chargesafter inadvertently or otherwise disabling a data feature.

In addition to the aspects and concepts developed above, a variety ofexemplary implementation possibilities and/or further details inconnection with the solutions provided herein will now be described. Ingeneral, it should be appreciated that all or a portion of the describedaspects can leverage, to the extent possible behaviors normally ascribedto architectural elements in use today. Thus, there is no need to fosternew crossover capabilities where it is unnecessary. For example, systemsor components designed or utilized to normalize and mediate incomingCDRs can continue to do so, while Enabler can be assigned ratingfunctions, and the billing systems or components can continue to betasked with billing for usage. Hence, the high-volume tasks assigned toeach of these components should be their only tasks, while assigningmore mundane utility tasks to other applications or components bettersuited to handle them.

As discussed supra, a few of the key objectives are to, e.g., evaluatethe combination of the end-user device in use, the rate plan, datafeatures, and all pertinent rules that regulate this combination, and toapply treatment, if necessary, or respond to the calling client withdata indicating which type of treatment is required. The aspectsdescribed can follow patterns already established and optionallyenforced by Device Eligibility Rules (DER), such as detection, rulesevaluations based upon the device, and assignment of treatment. UnlikeDER however, which tests whether a certain combination of device, plan,and/or features is compatible during the ordering phase (e.g., initialsign-up), the treatment service will evaluate how the subscriber isusing the provisioned data service, whether pertinent rules areviolated, and whether to apply treatment.

Notably, the described subject matter offers the host network anaccessible and highly configurable set of rules, attributes, andtreatment behaviors whose management is not necessarily tied to softwarereleases or deployments. Ideally, the strategic value of the treatmentservice should offer information technology or related departments awider spectrum of treatment possibilities than what is disclosed herein.

The following sections decompose one or more aspects of the disclosedsubject matter in a manner intended to underscore and further examinefunctional portions or components.

Detection

A fundamental question must be answered as to whether informationtechnology departments should react upon the detection of a device swapor whether it should wait until the device is used in violation of a setof rules. What is described herein is generally formulated with thelatter objective in mind. Thus, while the subject matter detailed can beapplied for such purpose, this disclosure is generally directed to casesin which it is chosen not to use available data to evaluate the intentof the subscriber to misuse the device and/or violate serviceagreements. It can be recognized that inherent latencies betweenmediation and results generated by Enabler, and further that treatmentcan be applied after a violation has been detected and evaluated.

Accordingly, detection should be performed by Enabler as it receives thedata EDR's (CSG-CDR and G-CDR). The suggested method to detect SIMswapping is for Enabler to compare the IMEI on the incoming CDR to theIMEI in an IMEI Master List. If found, then Enabler should compare thedevice's IMEI Type to the IMEI Type on the blacklist for thesubscriber's rate plan or data feature. If the IMEI Type is not found onthe blacklist for the provisioned rate plan or data feature, then noaction is required. If it is, then a treatment evaluation must takeplace.

For the sake of economy, Enabler can cache the results of its initialdetection whenever it detects the IMEI Type in use is on the blacklistfor the subscriber's rate plan or data feature. Additionally oralternatively, mediation departments or components can also be able todetect when a SIM is being used in a device that is blacklisted on therate plan or data feature; however, these features normally should behandled by Enabler rather than mediation.

Threshold detection normally should also be performed by Enabler tosupport Data Roaming Controls. The thresholds can be configured throughthe treatment service administrative interface with a variable number ofthreshold parameters—as well as the daily and billing cycle thresholds.Enabler should receive these and all global parameters from thetreatment service on a daily basis as reference data. Enabler should usethe threshold parameters to trigger a treatment event to the treatmentservice when the data roaming thresholds are breached.

Mediation

Network elements transporting data can provide IMEI data to mediationcomponents. Mediation can pass Enabler the IMEI when it receives it indata CDRs.

Rating

The host network service agreements can provide that subscribers toproducts without DER enabled will not usually receive treatment undervarious billing rules. Similar requirements might also provide that thehost network can select one or more existing plans or features that mustreceive treatment immediately. And finally, certain requirements mighteven restrict information technology departments or components fromconducting sweeps to replace the specified subscriber's plans or datafeatures with those that are DER enabled.

However, Enabler's real-time ability to detect when subscribers aregenerating data when using an IMEI not eligible for use according to therate plan or data feature's blacklist, make it possible to applytreatment to all subscribers, not just to those provisioned with newproducts.

In support of differential billing, the host network can use thetreatment service's administration interface to add any existingproducts it has selected for differential billing.

When Enabler detects that the IMEI Type in use is also on the blacklistfor the subscriber's rate plan or data feature, Enabler can send anevent to the treatment service for evaluation (e.g., DUCS). Thetreatment service can use the “DER Enabled” flag to determine whether toapply treatment. If the IMEIs are mismatched and the “DER Enabled” flagis set, the treatment service can automatically apply a designatedtreatment.

Data usage records (e.g., CDRs) rated by Enabler can contain some formof SIM swap indicator when appropriate, the IMEI device type should beentered into the event record, the date and time in the market oforigination for the usage, and the charged differential rate for theusage. For these and other aspects, Enabler is not necessarily testingthe device, rate plan and features against DER. Rather, Enabler canfacilitate sending the transaction to the treatment service forevaluation of treatment options per business rules.

Differential Rate

Differential rates are another type of billing rate applied under a setof variable conditions. Where the included and overage rates arefamiliar, the differential rate can be applied as a penalty whendifferential billing rules are violated.

Differential rates can be maintained via the administration a graphicaluser interface (GUI) for the Treatment Service, and can be applied toevent records by Enabler. A differential rate and a maximum chargeamount can be supplied by the treatment service as reference data toEnabler. After an evaluation has determined that the rate must beapplied to the subscriber's current data usage, Enabler can apply thedifferential rate. Enabler generally should use this higher ratethereafter as long as the incoming IMEI, the rate plan or data features,and the IMEI Type in the blacklist remain unchanged, and/or untilreaching the maximum charge limit for the billing cycle.

When the Subscriber's maximum charge limit has been met for a billingcycle, the differential rate will often expire. All other roaming andnon-Differential Billing charges can continue to be applied as usual.When a new billing cycle commences, the maximum rate charged shouldnormally be reset to zero. However, the differential rate should beapplied immediately if the conditions for its application haven'tchanged from the previous month. If the subscriber has fallen intocompliance before the previous billing cycle date, then the differentialrate will not apply at the outset of the new billing cycle.

When a subscriber replaces the device or modifies the rate plan or datafeatures, Enabler can retest the incoming IMEI in the manner describerabove. If the IMEI Type continues to violate the blacklist restriction,Enabler can again send an event to the treatment service for treatmentevaluation.

In some cases, a subscription may have various exemption SOC/features onit. If present, one SOC/feature can, e.g., inform the treatment serviceto send no notifications to the subscriber. Another SOC/feature, ifpresent, can, e.g., inform Enabler not to charge the differential rateand to return to charging the rates (in-bucket and out-of-bucket)provisioned on the data SOC/feature.

Data Roaming Thresholds

The host network may optionally require multiple subscriber thresholdsfor roaming data usage and multiple evaluation time periods. Such datausage thresholds can be adapted for ready configurability and whenmodified, can apply in near real-time or at least once per calendar day.The data roaming thresholds can be evaluated at the subscriber levelwhen CDRs are being rated or re-rated.

The threshold parameters that define when a threshold is breached can belisted here as categories of usage. When the maximum value in anycategory is reached, the threshold will have been breached. Suchcategories of usage can include, for instance:

-   -   Total domestic usage on-net    -   Total domestic usage off-net    -   Total usage on-net    -   Total usage off-net    -   International

Moreover, Enabler can record the PLMN of the off-net carrier when theoff-net data usage threshold is reached. Data Roaming Controls rules fortreatment can be applied by the treatment service. If an event is to besent to the treatment service, Enabler will supply enough data todescribe the event, to identify the subscriber, the private land mobilenetwork (PLMN) of another carrier for off-net data usage, and/or anyother pertinent data required by the service.

Enabler should continue sending the treatment service the thresholdevents, even after an exemption feature has been added to thesubscription. Data attributes in this event will generally emerge fromthe High-Level Design phase of implementation of the disclosed subjectmatter.

Billing

Selected products can also contain a list of one of more compatibledevices (white list) as is conventional. These lists should appear onproducts in the formal SID form. Products that require DER enforcementshould be created as such with the “DER Enabled” flag on the SID formset to true. DER currently prohibits ineligible device, rate plan,and/or feature combinations during the Ordering phase.

Several products will be created that can act to exempt the subscriber,TCM, account owner, and non-DCS Reseller from receiving thresholdnotifications triggered by Data Roaming Controls. One exemption productcan relate to a time-to-live for as long as the current billing cycle. Asecond product can be configured to have no expiration. Enabler may needmultiple rates: one for detected SIM swapping, another for detectedtethering, and others rates for differing situations.

Applicable usage charges can continue to accrue while the Subscriber isin violation of rules. Moreover, reports may be requested by the hostnetwork to measure the scope and effectiveness of any given program. Inaddition, notes added to the subscriptions as part of this program canflow to BID for future reports as they may be defined.

Bill Presentation

The detailed display of billed and unbilled differential usage chargeson various interfaces, whether in print media or on graphical userinterfaces, can be configured to indicate when a SIM swap was detected,the device used, and the charged differential rate. This information canbe used by the Subscriber, TCM, account owner, non-DCS Reseller,Customer Care Reps, and Sales Reps. This bill should display a newsummary line for the differential billed usage and separate data detailsections to call out the different categories of prohibited events suchas, e.g., prohibited SIM Swapping of Blackberry-like device, prohibitedtethering of PDA-like device, and so forth. The following list of userinterfaces that display detailed unbilled and billed data usage can berequired to be capable of displaying the information described above.

-   -   TLG CSM    -   Care client    -   PRM    -   OPUS    -   PDC1    -   PDC2    -   Premier Online Care (POC)    -   Premier    -   Phoenix    -   eBPP    -   OLAM

BMG accounts that have contracted to receive their statements on WinCDcan also be able to readily see such information. A notification of datasuspension can be sent when the treatment service suspends the dataservice. The subscription can be noted whenever a notification is sent.The note can be added using a reason code, and if necessary, a primaryreason code to further describe why it was added. These codes should beunique for the disclosed subject matter; however, in some cases existingcodes can be employed.

Subscribers who use OLAM to view their statement and/or unbilled datausage should be able to view the list of notifications sent to them as aresult of Data Roaming Controls enforcement. Subscribers whose datausage was restored from suspension should not be able to see thenotifications that lead to the recent suspension when using the OLAMscreen to view their account. Anytime the notification list is reset,the OLAM view of the Subscriber's account must no show previousnotifications.

Customer Care and Sales

The Data Roaming Controls treatment can consist of sendingnotifications, either or both SMS or email, based upon rules that definethresholds and the time of day to send the notifications. The hostnetwork can provide flexibility in this area, which can be managed bythe network through the treatment service's web based GUI. Notificationscan be sent according to rules previously described; however a customersupport representative (CSR) may add an exemption SOC/feature to theCustomer's subscription effectively turning off the notifications for aspecific time period. A CSR may also add an exemption SOC/feature toforce Enabler to rate data usage at the provisioned SOC/feature raterather than at the differential rate.

Depending on the pertinent methods and procedures (M&Ps) for thispurpose, a CSR may add either an exemption feature that has billingcycle duration, or one that never expires. These time-based exemptionfeature products should be configured in SID to be exclusive of eachother. The Indirect or Agent Sales clients (PDC1 and PDC2) might berequired to refuse to permit their users to either assign or to removethe exemption features.

When the CSR adds or removes a notification exemption SOC/feature,Customer Care and Retail Sales clients can pop a dialogue box that mustbe acknowledged before the Rep may continue. The text in the dialoguemust tell the Rep to notify the Subscriber, TCM, account owner, ornon-DCS Reseller that the responsibility to pay all data usage chargesremains theirs. Text box language can be provided by the business.

National Billing Operations, Retail Sales Reps, and Clarify Reps must beable to view the SIM swap indicator and the exemption SOC/features tosupport dispute resolution. Retail implementations of the disclosedsubject matter should also translate the device type to an Englishcommon name such as Blackberry or PDA or Lap top card.

Common Treatment Service (Data Usage Control Service (DUCS))

While DER can be contained within the billers, the test it conducts canprohibit incompatible or ineligible device, rate plan and/or featurecombinations during the Ordering phase. Unfortunately, in conventionalplatforms, this test often occurs too late in the Ordering phase andcauses numerous avoidable exceptions when a violation is detected. Inaddition, this contributes to a poor Customer experience just when theCompany is trying to make a good first impression.

The Common Treatment Service (CTS) is a new highly-available,disaster-recoverable service application. It can behave much like DER,but it can evaluate provided data against its rules set only after thedevice has been put into use on our network. Appreciably, the CTS can insome implementations fill the roll of DER, emerging as a much neededDecomposition Service to better suit I/T needs. CTS can receive datafrom Enabler, evaluate it against its rules, send events to the billersto add notes and SOC/features, and deliver reference data to Enabler forits use. Treatment is a core functionality of this service; much likenormalizing and mediating CDRs is the core function of the MediationService.

CTS Product Repository

CTS can receive new products created through the SID process, especiallythose with the “DER Enabled” flag set to true. The CTS Administratorwill store the data from the SID necessary for CTS to perform itsmission. The SOC/feature product that will be applied when theSubscriber's data usage reaches the defined thresholds must be createdby the Business. Any implementation of the disclosed subject mattershould support adding variables so the same product can be defined andreused in various ways for each threshold.

The supported variations of what this product can do are in the listbelow. CTS must support the placement of attributes on the product as itis sent to CSI to be placed on the subscription. The billing systemsshould recognize the attributes and convert them into the alreadydefined Switch Control events, such as:

-   -   Data restriction—all data, on and off net    -   Roaming restriction—all data and voice, all off net    -   Roaming restriction—all data and voice, international off net    -   Service suspension—all service on and off net    -   Service suspension and hot lining

Products that have device exclusions on them (in the form of a deviceblacklist) and permitted inclusions (device white list) will beextracted from the SID form and put into the CTS database. Productswhose attributes will be used to enforce Smart Data Controls arerequired to have a differential rate parameter. This parameter will bestored in the CTS database, but will be editable by the Business throughthe CTS user interface.

The host network generally must have complete control over thedifferential rates to be charged, markets and sub-markets, account typesand sub-types, specific zip codes, and device blacklists and white liststhat cause or condition the application of treatment. Similarly, thenetwork usually must be able to control the daily and billing cycle datausage threshold levels by total domestic off-net usage, total domesticon-net usage, total off-net usage, total on-net usage, and internationalusage.

The product database must also include the current master IMEI rangetable made available by Supply Chain. A recurring job must reliablyfetch this list. A CTS flag may be required on each applicable productfor future use and to decouple the DER products from usage treatmentbehavior. The HLDs should address this possibility after thoughtfulconsideration. An example of the need for this decoupling has emergedfrom Business Requirement DB.006, which requires that products havetypes assigned to them. Currently, the SID process may not assign therequired product types.

CTS Rules Repository

CTS rules should be stored in a database for easy maintenance, butshould be cached in memory for use. Rules should be assigned referencenumbers; e.g., (000-000) and priority numbers (00). CTS rules should beexpressed, editable, and viewable using common rules syntax. The userinterface should make maintenance simple, accessible, secure, andauditable.

Exemptions to rules can be permitted. These exemptions should apply tothe following criteria: Account type, account sub-type, BAN or accountnumber, FAN, or dial-able number. More exemptions may be provided overtime by the Business. Adding rules through the user interface shouldsupport adding one rule or adding a group of affiliated rules.

The interface should support setting rules to active or inactive at theBAN or account level, Subscriber level, on specific rate plans andSOC/features, and on specific rate plan or feature types. Such settingsshould become effective in near real-time locally and at least once percalendar day via a nightly sync with Enabler. Conditional andconfigurable scoping parameters may also apply at various times to guideCTS in how and when to apply treatment. The parameters listed below andtheir values may be configured through the treatment serviceadministrative interface. The parameters need not be designed to beunique and may occur many times in various combinations with otherparameters, such as:

-   -   Rate plan    -   Account type    -   Account sub-type    -   Liability (IRU or CRU)    -   Owner Code (Applies to DSC Resellers)    -   Device type (IMEI Type)    -   Tenure    -   Billed data in the previous billing cycle    -   All markets    -   Select markets    -   Select sub-markets    -   Zip code

Rules and related actions may be created at any time in the treatmentservice. The nightly sync-up of various rules and thresholds between thetreatment service and Enabler is expected to occur only once per day.Therefore, if Enabler fails to properly handle some criteria, or if ituses out-of-date criteria, the treatment service can evaluate the eventagainst the current rule and will invoke the correct action. Theapplication of rules should be recorded in the CTS database for reportsthat may be required as part of this project. Reporting schema should besupplied by the host network.

CTS Programmatic Interface

CTS should expose its methods using a common simple object accessprotocol (SOAP) interface. The SOAP can build various interface methodsto support its mission. The CTS team should publish its schema, createon-boarding kits, and generally support developers to enable its use.The input data should consist of these optional and required elements:IMEI, IMSI, BAN, billing cycle date, threshold number (i.e. 1-n),unbilled data usage, and the billed data usage from the previous billingcycle. The CTS output data should consist of optional and requiredelements; for example a unique sequence number and the result of therule evaluation. CTS should expose a public method that returns thetreatment history by Subscriber for reporting purposes. The call mightrequire an optional date that constrains the volume of data returned tothe calling client.

CTS Native Capabilities

At the core of CTS is a rules engine, a set of rules, and a list oftreatment actions. The recommendation of this solution is to reuse thesame technology currently used by BMG and the Common Product Catalog(CPC). Rules in CTS should evaluate provided data and, when necessary,apply a treatment and/or respond with treatment data to a callingclient. For example, CTS must expose a programmatic interface that canreceive events from Enabler containing data it will evaluate againstexisting rules.

CTS should have an accessible and secure graphical user interface forthose responsible to manage the rules and treatment actions for thisprogram. CTS must use the AIM security framework to provideauthentication access controls to this service application. CTS willalso want to create local authorization controls to manage roles. CTSrules and data must be easily configurable and then applied in real-timeor on a configured effective date. Rules should be easily set to expireon a configured date as well.

Notification messages can be stored in CTS as treatment data. Thecontent of the messages must be easily editable through the userinterface. Each notification message must include attributes thatsupport a range of time each day the message may be sent, as well as thenumber of times per day or per billing cycle that the message may besent. CTS should be able to call several CSI methods as required tofulfill its treatment mission. For example, if a treatment prescribesadding a SOC/feature or a note to a subscription, CTS will call CSI'sUpdateSubscriberProfileRequest( ) or AddNote( ) methods, respectively,to perform this action.

CTS can be enabled to send notifications through CSI to the EnterpriseDocument Delivery system (EDD), a system that will send SMS and emailmessages. EDD can also send regular mail, such as postcards, should itbecome necessary when the first two methods are unavailable. The sourceof the email address must come from the following locations in thesequence provided:

-   -   CRU—BAN, BASE account, subscription    -   IRU/Consumer—subscription, BAN    -   DCS Resellers (e.g., Concord, Northstate, Home Telco and        Farmers)—DCS Reseller account

CTS should be able to send language-specific notifications, depending onthe Subscriber's indicated preference. CTS can observe a configured timeof day when a notification must be sent. The time of day should berelative to the time in the Subscriber's market and sub-market. Systemtime should be mapped to each market and sub-market using GMT plus theoffset. This will make it easier to deploy CTS into multiple datacenters without regard to system time. CTS can generate a uniquesequence number. This artifact verifies that CTS was used to evaluatethe provided data and will satisfy the implied workflow requirement. Inaddition, CTS can log all rule evaluations and treatments, and recordrule evaluations even though treatment may not have been applied.

Notification Messages

This section describes the construction and type of notificationmessages that can be utilized by the disclosed subject matter. Inparticular, notifications can relate to:

-   -   Email notifications that can include the dial-able number on the        subject line.    -   Notifications can include an AT&T callback number.    -   SMS and email notification message content will be provided by        the Business using the CTS graphical interface.    -   The content of SMS and email notifications will be editable by        the Business using the CTS user interface.    -   Notification EDRs for messages sent under this program will be        dropped by Enabler.    -   The requirements for differential billing limit to one the        number of times per day that message notifications may be sent.    -   Differential billing message notifications may be sent each day        of a billing cycle while a violation persists up to a        configurable maximum number of times. The Business will be able        to set this maximum number using the CTS user interface.    -   The message notifications will be counted as they're sent during        each billing cycle. The count will be reset on the billing cycle        date.    -   Notifications must be sent immediately and no later than 24        hours after the rule violation was detected.

CTS Treatment Behavior for Smart Data Controls

This section will describe the scope of treatments CTS may apply asrequired by this project.

A rule generally must determine the eligibility of the combination ofthe “DER Enabled” flag, the rate plan or data features, and the devicebeing used. The input data should consist of the billing cycle date. Theresponse to the calling client generally must include a violation code,and the unique sequence number. If the evaluation of the combinationviolates rules, then treatment will be applied as follows:

-   -   A pertinent SMS must be sent immediately to the Subscriber's        device.    -   A pertinent email must be sent immediately to the appropriate        email address.    -   If Subscriber belongs to a DCS Reseller, the pertinent email        must be sent immediately to the Reseller address.

For the following threshold rule violations, CTS must apply treatment.The list of thresholds may be expanded beyond the examples in the listbelow.

-   -   Threshold 1—For DCS Resellers, send an email notification to the        Reseller.    -   Threshold 1—For non-DCS Resellers, send an SMS to the        Subscriber's device.    -   Threshold 1—For non-DCS Resellers, send an email to the        Subscriber's email address.    -   Threshold 1—For non-DCS Resellers, send an email to the BMG BASE        account's TCM email address.    -   Threshold 1—For non-DCS Resellers, send an email to the account        owner.    -   Threshold 1—For all Subscribers, optionally apply a SOC/feature        to the subscription. This SOC/feature will be described by the        Business.    -   Threshold 2—For all Subscribers, add a SOC/feature to the        subscription.    -   Threshold 2—For DCS Resellers, send an email notification to the        Reseller.    -   Threshold 2—For non-DCS Resellers, send an SMS to the        Subscriber's device.    -   Threshold 2—For non-DCS Resellers, send an email to the        Subscriber's email address.    -   Threshold 2—For non-DCS Resellers, send an email to the BMG BASE        account's TCM email address.    -   Threshold 2—For non-DCS Resellers, send an email to the account        owner.

Notification messages required for differential billing tests must besent only once per billing cycle to the account owners, telecommanagers, and DCS Resellers. Anytime a notification message is sent, anote describing the fact should be added to the subscription. An IMEIthat cannot be identified using the IMEI Master list can be authorizedby default to generate data usage without treatment. Notificationmessages can be sent when required, even when both thresholds arereached within a short evaluation period.

CTS should send an event to the Fraud application when the firstthreshold has been reached. The message protocol and schema should bedefined by the fraud application team. Data supplied in the event shouldinclude data from the following attributes:

-   -   Unbilled data usage by location (on-net, off-net, international)    -   Time period (daily or billing cycle)    -   PLMN of the other carrier at the point the roaming threshold was        reached    -   If available, Subscriber's rate plan and data features, Account        type and sub-type, liability type, device type, tenure, total        billed usage in the previous billing cycle.

Reporting

All reports containing detailed data usage should capture the SIM swapindicator.

Interfaces

Enabler can create a private interface that can receive responses fromCTS. In addition, Enabler should respond to calls for unbilled datausage by providing an optional device friendly name, and SIM swap andtethering indicators.

CTS can create a public, secure interface that will receive events fromEnabler.

CSI may be impacted if it is required to make its private email methodpublic for this project. Will need to transport the device friendly nameon one or more calls (especially the InquireUnbilledusage( ) call). Mayalso need to transport the SIM and tethering indicators in the samecalls. Will need to transport the optional TCM email address in theresponse to the InquireFANProfile( ) call. Will need to handle the TCMemail address coming back from the BASE FAN profile stored procedurecall.

CAM typically will need to transport the device friendly name on one ormore calls. Furthermore, CAM can also be required to transport the SIMand tethering indicators in the same calls; and might need to respond toan inquiry for all notification notes, or notes by reason code orprimary action code added to subscription during a specified billingcycle.

iPOS generally will need to transport the device friendly name on one ormore calls. Additionally iPOS can also be required to transport the SIMand tethering indicators in the same calls.

CEF can transport notes, reason codes, and/or primary action codes fromCAM for inquiries made by OLAM.

New Application(s) and/or Potentially Impacted Systems

-   -   TLG CSM—Applications that have billed and unbilled screens must        display the differential rate when applied. If not currently        doing so, must display the friendly device name used to generate        the differential charge and the SIM swap and/or tethering        indicators when present. Provide a pop-up dialogue box when CSR        adds or removes an exemption feature. Provide a pop-up dialogue        box when CSR removes a data suspension SOC/feature. The pop-ups        should be acknowledged by selecting a checkbox.    -   Care client—Applications that have billed and unbilled screens        must display the differential rate when applied. If not        currently doing so, must display the friendly device name used        to generate the differential charge and the SIM swap and/or        tethering indicators when present. Provide a pop-up dialogue box        when CSR adds or removes an exemption feature. Provide a pop-up        dialogue box when CSR removes a data suspension SOC/feature. The        pop-ups should be acknowledged by selecting a checkbox.    -   PRM (DCS Resellers)—Applications that have billed and unbilled        screens must display the differential rate when applied. If not        currently doing so, must display the friendly device name used        to generate the differential charge and the SIM swap and/or        tethering indicators when present. Provide a pop-up dialogue box        when CSR adds or removes an exemption feature. Provide a pop-up        dialogue box when CSR removes a data suspension SOC/feature. The        pop-ups should be acknowledged by selecting a checkbox.    -   OPUS—Applications that have billed and unbilled screens must        display the differential rate when applied. If not currently        doing so, must display the friendly device name used to generate        the differential charge and the SIM swap and/or tethering        indicators when present. Provide a pop-up dialogue box when CSR        adds or removes an exemption feature. Provide a pop-up dialogue        box when CSR removes a data suspension SOC/feature. The pop-ups        should be acknowledged by selecting a checkbox.    -   PDC1—Applications that have billed and unbilled screens must        display the differential rate when applied. If not currently        doing so, must display the friendly device name used to generate        the differential charge and the SIM swap and/or tethering        indicators when present.    -   PDC2—Applications that have billed and unbilled screens must        display the differential rate when applied. If not currently        doing so, must display the friendly device name used to generate        the differential charge and the SIM swap and/or tethering        indicators when present.    -   Premier Online Care (POC)—Applications that have billed and        unbilled screens must display the differential rate when        applied. If not currently doing so, must display the friendly        device name used to generate the differential charge and the SIM        swap and/or tethering indicators when present. Must display new        note regarding data suspension.    -   Premier—Applications that have billed and unbilled screens must        display the differential rate when applied. If not currently        doing so, must display the friendly device name used to generate        the differential charge and the SIM swap and/or tethering        indicators when present. Provide a pop-up dialogue box when CSR        adds or removes an exemption feature. Provide a pop-up dialogue        box when CSR removes a data suspension SOC/feature. The pop-ups        should be acknowledged by selecting a checkbox. Must provide        viewing access to SOC/features dealing with exemptions and        suspension, but must disallow TCMs from provisioning or        de-provisioning these SOC/features.    -   Phoenix—Must display new note regarding data suspension. Provide        a pop-up dialogue box when CSR adds or removes an exemption        feature. Provide a pop-up dialogue box when CSR removes a data        suspension SOC/feature. The pop-ups should be acknowledged by        selecting a checkbox.    -   eBPP—Applications that have billed and unbilled screens must        display the differential rate when applied. If not currently        doing so, must display the friendly device name used to generate        the differential charge and the SIM swap and/or tethering        indicators when present. Must display new note regarding data        suspension.    -   OLAM—Applications that have billed and unbilled screens must        display the differential rate when applied. If not currently        doing so, must display the friendly device name used to generate        the differential charge and the SIM swap and/or tethering        indicators when present. Must display new notes regarding data        suspension. Must display notifications sent to the Subscriber        during the billing cycle. Must clear notifications sent during        the billing cycle if they exceed their effective time (i.e.        daily notifications). Must clear notifications if the Subscriber        resumes service after suspension.    -   Enabler—Must interact with CTS to properly apply treatment. Must        send an event to CTS when necessary to apply treatment for data        roaming threshold breaches. Must identify Subscriber's by        account, account type, or SOC/feature in order to exempt these        Subscribers from being billed at the differential rate. Enabler        will use reference data supplied by CTS for this purpose. Must        translate an EDR's IMEI to IMEI Type using the IMEI Master List.        Must compare IMEI Type with the IMEI Type on the blacklist        accompanying the Subscriber's provisioned data product. Must add        two columns for SIM swap indicator and Tethering. Must map the        IMEI of the device used to a friendly device make and model and        add it to the event record.    -   Mediation—Must pass the IMEI in EDR's to Enabler.    -   Common Treatment Service—New service application    -   CARE billing system—Must save SIM and tethering swapping        indicator. Must provide these indicators for detailed bill        presentation. Must accept data service suspension feature/SOC        and its dynamic parameters and send the appropriate control data        to Switch Control.    -   TLG billing system—Must save SIM and tethering swapping        indicator. Must provide these indicators for detailed bill        presentation. Must accept data service suspension feature/SOC        and its dynamic parameters and send the appropriate control data        to Switch Control.    -   CSI—Must on-board CTS, a new service application. May also be        required to make an email method public. Must transport the        optional device “friendly name” (make & model) in response to        clients calling CSI's InquireUnbilledUsage( ) method. May be        impacted to transport the optional SIM swap and tethering        indicators. Must handle the new optional TCM email address        attribute in the response to the FAN profile stored procedure        call. Must vend the optional TCM email address to the treatment        service.    -   CAM—Must transport the optional device “friendly name” (make &        model) in response to clients calling for unbilled usage. May be        impacted to transport the optional SIM swap and tethering        indicators. Must develop a method to permit clients to inquire        for all notification notes, or notes by reason code, primary        action code, or by another unspecified notes attribute on a        subscription during a specified billing cycle.    -   BASE—Must return the optional TCM email address in the stored        procedure call for FAN profile data.    -   CEF—Must call a method in CAM to inquire for all notification        notes, or notes by reason code, primary action code, or by        another unspecified notes attribute on a subscription during a        specified billing cycle.    -   TLG API—Must transport the optional device “friendly name” (make        & model) in response to clients calling for unbilled usage. May        be impacted to transport the optional SIM swap and tethering        indicators.    -   BID—Must provide reports to be specified by the Business.    -   Fraud Data Transformer—Must receive Data Roaming threshold        events generated by CTS    -   Clarify—Must be able to open tickets and resolve issues related        to this program. Must be able to call CTS for historical        treatment.    -   iPOS—Must transport the optional device “friendly name” (make &        model) in response to clients calling for unbilled usage. May be        impacted to transport the optional SIM swap and tethering        indicators.    -   System X—Applications that have billed and unbilled screens must        display the differential rate when applied. If not currently        doing so, must display the friendly device name used to generate        the differential charge and the SIM swap and/or tethering        indicators when present. Provide a pop-up dialogue box when CSR        adds or removes an exemption feature. Provide a pop-up dialogue        box when CSR removes a data suspension SOC/feature. The pop-ups        should be acknowledged by selecting a checkbox.    -   Oasys/Centaur—Must accept the exemption product(s) category        attribute to enable the display of the information dialogue box        to the Rep. This attribute will be stored locally with other        product data coming from SID.

With reference now to FIG. 5, illustration 500 depicts an exemplarydecision path associated with a particular SOC. Accordingly,illustration 500 assumes the case of a particular service agreementand/or SOC, here denoted as SOC=1, as indicated by reference numeral502. Under such a service plan, if the location of data usage is fromthe subscriber's home, then the decision path flows as indicated byreference numeral 504. However, if the location is described by domesticoff-net and/or roaming, or international, then flow traverses paths 506or 508, respectively.

Since each decision path represents a distinct type of data usage,thresholds can be set accordingly. In this case, for home data usage,example thresholds are set at 500 KB per day or 10,000 KB per billingcycle; for roaming, example thresholds are set at 100 KB per day or2,000 KB per billing cycle; and for international, settings are for 25KB per day or 500 KB per billing cycle as denoted by reference numerals510, 512, and 514, respectively. If any such threshold is breached,which can be determined by the Enabler, then flow can proceed to theDUCS system, wherein treatment 304 can be determined for any given case.Thus, at reference numeral 516, 518, 520, suitable treatment 304 can bedetermined such as sending notification 306, adjusting usage (e.g., viaupdate 312), adding a note, adding a SOC or feature (e.g., also viaupdate 312), creating audit trail 408 and so forth.

However, it should be appreciated that applying treatment 304 can befirst premised on certain exemptions or the like. Thus, if thesubscriber meets criteria associated with exemption 522, 524, or 526,the treatment 304 need not be applied. However, if not, then treatment304 can be applied, or in some cases no treatment, but with an audittrail instantiated, at reference numerals 528, 530, or 532.

Now turning to FIG. 6, system 600 that can perform or aid with variousdeterminations or inferences is illustrated. Generally, system 600 caninclude detection component 108 and control service component 302 assubstantially described herein. In addition to what has been described,the above-mentioned components can make intelligent determinations orinferences. For example, Bayesian probabilities or confidence measurescan be employed or inferences can be based upon machine learningtechniques related to historical analysis, feedback, and/or previousdeterminations or inferences.

For instance, detection component 108 can intelligently determine orinfer when to issue usage inequity 110 as well as other suitableinferences relating to detecting or evaluating data usage, service plansor features, or the like. Similarly, control service component 302 canintelligently determine or infer suitable treatment 304, when or whetherto apply treatment 304, whether or not to initiate an audit trail, andso forth. It should be understood, determinations or inferences detailedherein can themselves rely upon previous or base intelligentdeterminations or inferences.

In addition, system 600 can also include intelligence component 602 thatcan provide for or aid in various inferences or determinations. Inparticular, in accordance with or in addition to what has been describedsupra with respect to intelligent determinations or inferences providedby various components described herein, e.g., all or portions ofdetection component 108 or control service component 302 and/or Enableror DUCS. Additionally or alternatively, all or portions of intelligencecomponent 602 can be included in one or more components describedherein. Moreover, intelligence component 602 will typically have accessto all or portions of data sets described herein, such as data store114.

Accordingly, in order to provide for or aid in the numerous inferencesdescribed herein, intelligence component 602 can examine the entirety ora subset of the data available and can provide for reasoning about orinfer states of the system, environment, and/or user from a set ofobservations as captured via events and/or data. Inference can beemployed to identify a specific context or action, or can generate aprobability distribution over states, for example. The inference can beprobabilistic—that is, the computation of a probability distributionover states of interest based on a consideration of data and events.Inference can also refer to techniques employed for composinghigher-level events from a set of events and/or data.

Such inference can result in the construction of new events or actionsfrom a set of observed events and/or stored event data, whether or notthe events are correlated in close temporal proximity, and whether theevents and data come from one or several event and data sources. Variousclassification (explicitly and/or implicitly trained) schemes and/orsystems (e.g., support vector machines, neural networks, expert systems,Bayesian belief networks, fuzzy logic, data fusion engines . . . ) canbe employed in connection with performing automatic and/or inferredaction in connection with the disclosed subject matter.

A classifier can be a function that maps an input attribute vector,x=(x1, x2, x3, x4, xn), to a confidence that the input belongs to aclass, that is, f(x)=confidence(class). Such classification can employ aprobabilistic and/or statistical-based analysis (e.g., factoring intothe analysis utilities and costs) to prognose or infer an action that auser desires to be automatically performed. A support vector machine(SVM) is an example of a classifier that can be employed. The SVMoperates by finding a hyper-surface in the space of possible inputs,where the hyper-surface attempts to split the triggering criteria fromthe non-triggering events. Intuitively, this makes the classificationcorrect for testing data that is near, but not identical to trainingdata. Other directed and undirected model classification approachesinclude, e.g., naïve Bayes, Bayesian networks, decision trees, neuralnetworks, fuzzy logic models, and probabilistic classification modelsproviding different patterns of independence can be employed.Classification as used herein also is inclusive of statisticalregression that is utilized to develop models of priority.

FIGS. 7, 8, and 9 illustrate various methodologies in accordance withthe disclosed subject matter. While, for purposes of simplicity ofexplanation, the methodologies are shown and described as a series ofacts, it is to be understood and appreciated that the disclosed subjectmatter is not limited by the order of acts, as some acts may occur indifferent orders and/or concurrently with other acts from that shown anddescribed herein. For example, those skilled in the art will understandand appreciate that a methodology could alternatively be represented asa series of interrelated states or events, such as in a state diagram.Moreover, not all illustrated acts may be required to implement amethodology in accordance with the disclosed subject matter.Additionally, it should be further appreciated that the methodologiesdisclosed hereinafter and throughout this specification are capable ofbeing stored on an article of manufacture to facilitate transporting andtransferring such methodologies to computers. The term article ofmanufacture, as used herein, is intended to encompass a computer programaccessible from any computer-readable device, carrier, or media.

Turning now to FIG. 7, an exemplary method 700 for automatically ordynamically detecting or remedying service usage inequities for acommunications network is illustrated. Generally, at reference numeral702, one or more CDR associated with a communication transaction of asubscriber to the communications network can be obtained. Thecommunication transaction can relate to either voice or data. Forexample, the communication transaction can be a call session, a datasession, and so forth.

In addition, at reference numeral 704, additional subscriber informationrelating to service agreements or to features, options, terms,conditions, or rules data related thereto can be obtains. Accordingly,at reference numeral 706, CDR data relating to communicationtransactions obtain in connection with reference numeral 702 can becompared to the additional subscriber information obtained in connectionwith reference numeral 704. Based upon this comparison, a usage inequitycan be identified. Thus, at reference numeral 708, a data usage eventmessage describing the usage inequity can be output.

With reference now FIG. 8, exemplary method 800 for providing variousadditional features or aspects in connection with identifying a usageinequity or other Enabler functionality is illustrated. At referencenumeral 802, the usage inequity determined at reference numeral 706 canbe determined when avoidable high data usage charges are inferred toarise during a current billing cycle. Such can relate to potential orforecasted overages charges or the like. Similarly, at reference numeral804, the usage inequity can be determined when usage of thecommunication network violates a provisioned service agreement agreed toby the subscriber.

For example, usage that violates a provisioned service agreement can bedetermined according to reference numeral 806, which provides that anInternational Mobile Equipment Identifier (IMEI) included in the CDRretrieved at reference numeral 702 can be translated to an IMEI Typethat indicates a type or class of equipment employed for thecommunication transaction associated with the CDR. Hence, at referencenumeral 808, the IMEI Type can be compared to allowable equipmentincluded in the additional subscriber information obtained in connectionwith reference numeral 704 or to a blacklist equipment list particularto a service agreement associated with the subscriber.

At reference numeral 810, the IMEI can be utilized for detecting anunauthorized subscriber information module (SIM) swap of for detectingan unauthorized communication-based device tethering. At referencenumeral 812, the data usage event message can be output substantially inreal time.

Turning briefly to FIG. 9, an exemplary method 900 for providing variousaddition features or aspects in connection with determining treatment orother DUCS functionality is depicted. At reference numeral 902, aninterface for enabling authorized administrators can be provided,enabling creation of or update to rules data. Rules data can be storedfor later access or recall.

For example, at reference numeral 904, a treatment to apply can bedetermined based upon the data usage event message and the rules data.The treatment can relate to, e.g., a notification to the subscriber,wherein the notification includes one or more of the usage inequity,suggested remedies, potential actions should the usage inequitycontinue, or further contact information; additional or more detailedmonitoring of data usages associated with the subscriber; a restrictionto data usage or services associated with the subscriber; a terminationof data usage or services associated with the subscriber, and so on.

Regardless of the particular treatment determined or inferred, butassuming such treatment at least includes a determination that anotification is suitable, then at reference numeral 906, thenotification can be propagated to the subscriber by way of at least oneof SMS, email, or mail. Furthermore, at reference numeral 908, an updateto a provisioned service or to an agreement thereof or to associatedfeatures can be automatically facilitated, e.g., when the subscriberauthorizes the update or requests an exemption in response to thenotification provided at reference numeral 906. For instance, thenotification can indicate that the subscriber can potentially save moneyby upgrading or downgrading his or her service. Along with thisnotification, a request for the subscriber to authorize the change canbe provided as well, allowing the subscriber to, e.g., select “I agree”or the like, and return this authorization via SMS or another way. Asanother example, the notification can indicate a usage violation due to,say, a SIM swap to an unauthorized device. Rather than being subject tovarious treatments, the subscriber can instead request an exemption,with can be agreed to, generally at the discretion of the host network,although potentially based upon an inference or rule.

At reference numeral 910, application of treatment (e.g., treatmentdetermined in connection with reference numeral 904) can be avoided orignored, especially in the case of a newly created or newly updated ruleto provide a “soak” period for the rule or update. During thisprovisional or “soak” period, or for other reasons, at reference numeral912, an audit trail for measuring or tracking the effects of treatment(e.g., what treat can potentially remedy or mitigate) defined by thenewly created or newly updated rule.

To provide further context for various aspects of the subjectspecification, FIG. 10 illustrates an example wireless communicationenvironment 1000, with associated components that can enable operationof a femtocell enterprise network in accordance with aspects describedherein. Wireless communication environment 1000 includes two wirelessnetwork platforms: (i) A macro network platform 1010 that serves, orfacilitates communication) with user equipment 1075 via a macro radioaccess network (RAN) 1070. It should be appreciated that in cellularwireless technologies (e.g., 4G, 3GPP UMTS, HSPA, 3GPP LTE, 3GPP UMB),macro network platform 1010 is embodied in a Core Network. (ii) A femtonetwork platform 1080, which can provide communication with UE 1075through a femto RAN 1090, linked to the femto network platform 1080through a routing platform 102 via backhaul pipe(s) 1085, whereinbackhaul pipe(s) are substantially the same a backhaul link 3853 below.It should be appreciated that femto network platform 1080 typicallyoffloads UE 1075 from macro network, once UE 1075 attaches (e.g.,through macro-to-femto handover, or via a scan of channel resources inidle mode) to femto RAN.

It is noted that RAN includes base station(s), or access point(s), andits associated electronic circuitry and deployment site(s), in additionto a wireless radio link operated in accordance with the basestation(s). Accordingly, macro RAN 1070 can comprise various coveragecells like cell 1205, while femto RAN 1090 can comprise multiple femtoaccess points. As mentioned above, it is to be appreciated thatdeployment density in femto RAN 1090 is substantially higher than inmacro RAN 1070.

Generally, both macro and femto network platforms 1010 and 1080 includecomponents, e.g., nodes, gateways, interfaces, servers, or platforms,that facilitate both packet-switched (PS) (e.g., internet protocol (IP),frame relay, asynchronous transfer mode (ATM)) and circuit-switched (CS)traffic (e.g., voice and data) and control generation for networkedwireless communication. In an aspect of the subject innovation, macronetwork platform 1010 includes CS gateway node(s) 1012 which caninterface CS traffic received from legacy networks like telephonynetwork(s) 1040 (e.g., public switched telephone network (PSTN), orpublic land mobile network (PLMN)) or a SS7 network 1060. Circuitswitched gateway 1012 can authorize and authenticate traffic (e.g.,voice) arising from such networks. Additionally, CS gateway 1012 canaccess mobility, or roaming, data generated through SS7 network 1060;for instance, mobility data stored in a VLR, which can reside in memory1030. Moreover, CS gateway node(s) 1012 interfaces CS-based traffic andsignaling and gateway node(s) 1018. As an example, in a 3GPP UMTSnetwork, gateway node(s) 1018 can be embodied in gateway GPRS supportnode(s) (GGSN).

In addition to receiving and processing CS-switched traffic andsignaling, gateway node(s) 1018 can authorize and authenticate PS-baseddata sessions with served (e.g., through macro RAN) wireless devices.Data sessions can include traffic exchange with networks external to themacro network platform 1010, like wide area network(s) (WANs) 1050; itshould be appreciated that local area network(s) (LANs) can also beinterfaced with macro network platform 1010 through gateway node(s)1018. Gateway node(s) 1018 generates packet data contexts when a datasession is established. To that end, in an aspect, gateway node(s) 1018can include a tunnel interface (e.g., tunnel termination gateway (TTG)in 3GPP UMTS network(s); not shown) which can facilitate packetizedcommunication with disparate wireless network(s), such as Wi-Finetworks. It should be further appreciated that the packetizedcommunication can include multiple flows that can be generated throughserver(s) 1014. It is to be noted that in 3GPP UMTS network(s), gatewaynode(s) 1018 (e.g., GGSN) and tunnel interface (e.g., TTG) comprise apacket data gateway (PDG).

Macro network platform 1010 also includes serving node(s) 1016 thatconvey the various packetized flows of information or data streams,received through gateway node(s) 1018. As an example, in a 3GPP UMTSnetwork, serving node(s) can be embodied in serving GPRS support node(s)(SGSN).

As indicated above, server(s) 1014 in macro network platform 1010 canexecute numerous applications (e.g., location services, online gaming,wireless banking, wireless device management . . . ) that generatemultiple disparate packetized data streams or flows, and manage (e.g.,schedule, queue, format . . . ) such flows. Such application(s), forexample can include add-on features to standard services provided bymacro network platform 1010. Data streams can be conveyed to gatewaynode(s) 1018 for authorization/authentication and initiation of a datasession, and to serving node(s) 1016 for communication thereafter.Server(s) 1014 can also effect security (e.g., implement one or morefirewalls) of macro network platform 1010 to ensure network's operationand data integrity in addition to authorization and authenticationprocedures that CS gateway node(s) 1012 and gateway node(s) 1018 canenact. Moreover, server(s) 1014 can provision services from externalnetwork(s), e.g., WAN 1050, or Global Positioning System (GPS)network(s) (not shown). It is to be noted that server(s) 1014 caninclude one or more processor configured to confer at least in part thefunctionality of macro network platform 1010. To that end, the one ormore processor can execute code instructions stored in memory 1030, forexample.

In example wireless environment 1000, memory 1030 stores informationrelated to operation of macro network platform 1010. Information caninclude business data associated with subscribers; market plans andstrategies, e.g., promotional campaigns, business partnerships;operational data for mobile devices served through macro networkplatform; service and privacy policies; end-user service logs for lawenforcement; and so forth. Memory 1030 can also store information fromat least one of telephony network(s) 1040, WAN(s) 1050, or SS7 network1060, enterprise NW(s) 1065, or service NW(s) 1067.

Femto gateway node(s) 1084 have substantially the same functionality asPS gateway node(s) 1018. Additionally, femto gateway node(s) 1084 canalso include substantially all functionality of serving node(s) 1016. Inan aspect, femto gateway node(s) 1084 facilitates handover resolution,e.g., assessment and execution. Further, control node(s) 1020 canreceive handover requests and relay them to a handover component (notshown) via gateway node(s) 1084. According to an aspect, control node(s)1020 can support RNC capabilities and can be substantially similar tothe control component 320 (FIG. 3) and can include functionalitythereof.

Server(s) 1082 have substantially the same functionality as described inconnection with server(s) 1014. In an aspect, server(s) 1082 can executemultiple application(s) that provide service (e.g., voice and data) towireless devices served through femto RAN 1090. Server(s) 1082 can alsoprovide security features to femto network platform. In addition,server(s) 1082 can manage (e.g., schedule, queue, format . . . )substantially all packetized flows (e.g., IP-based, frame relay-based,ATM-based) it generates in addition to data received from macro networkplatform 1010. It is to be noted that server(s) 1082 can include one ormore processor configured to confer at least in part the functionalityof macro network platform 1010. To that end, the one or more processorcan execute code instructions stored in memory 1086, for example.

Memory 1086 can include information relevant to operation of the variouscomponents of femto network platform 1080. For example operationalinformation that can be stored in memory 1086 can comprise, but is notlimited to, subscriber information; contracted services; maintenance andservice records; femto cell configuration (e.g., devices served throughfemto RAN 1090; access control lists, or white lists); service policiesand specifications; privacy policies; add-on features; and so forth.

It is noted that femto network platform 1080 and macro network platform1010 can be functionally connected through one or more reference link(s)or reference interface(s). In addition, femto network platform 1080 canbe functionally coupled directly (not illustrated) to one or more ofexternal network(s) 1040, 1050, 1060, 1065 or 1067. Reference link(s) orinterface(s) can functionally link at least one of gateway node(s) 1084or server(s) 1086 to the one or more external networks 1040, 1050, 1060,1065 or 1067.

FIG. 11 illustrates a wireless environment that includes macro cells andfemtocells for wireless coverage in accordance with aspects describedherein. In wireless environment 1150, two areas 1105 represent “macro”cell coverage, each macro cell is served by a base station 1110. It canbe appreciated that macro cell coverage area 1105 and base station 1110can include functionality, as more fully described herein, for example,with regard to system 1100. Macro coverage is generally intended toserve mobile wireless devices, like UE 1120 _(A), 1120 _(B), in outdoorslocations. An over-the-air wireless link 115 provides such coverage, thewireless link 1215 comprises a downlink (DL) and an uplink (UL), andutilizes a predetermined band, licensed or unlicensed, of the radiofrequency (RF) spectrum. As an example, UE 1120 _(A), 1120 _(B) can be a3GPP Universal Mobile Telecommunication System (UMTS) mobile phone. Itis noted that a set of base stations, its associated electronics,circuitry or components, base stations control component(s), andwireless links operated in accordance to respective base stations in theset of base stations form a radio access network (RAN). In addition,base station 1110 communicates via backhaul link(s) 1151 with a macronetwork platform 1160, which in cellular wireless technologies (e.g.,3rd Generation Partnership Project (3GPP) Universal MobileTelecommunication System (UMTS), Global System for Mobile Communication(GSM)) represents a core network.

In an aspect, macro network platform 1160 controls a set of basestations 1110 that serve either respective cells or a number of sectorswithin such cells. Base station 1110 comprises radio equipment 1114 foroperation in one or more radio technologies, and a set of antennas 1112(e.g., smart antennas, microwave antennas, satellite dish(es) . . . )that can serve one or more sectors within a macro cell 1105. It is notedthat a set of radio network control node(s), which can be a part ofmacro network platform; a set of base stations (e.g., Node B 1110) thatserve a set of macro cells 1105; electronics, circuitry or componentsassociated with the base stations in the set of base stations; a set ofrespective OTA wireless links (e.g., links 1115 or 1116) operated inaccordance to a radio technology through the base stations; and backhaullink(s) 1155 and 1151 form a macro radio access network (RAN). Macronetwork platform 1160 also communicates with other base stations (notshown) that serve other cells (not shown). Backhaul link(s) 1151 or 1153can include a wired backbone link (e.g., optical fiber backbone,twisted-pair line, T1/E1 phone line, a digital subscriber line (DSL)either synchronous or asynchronous, an asymmetric ADSL, or a coaxialcable . . . ) or a wireless (e.g., line-of-sight (LOS) or non-LOS)backbone link. Backhaul pipe(s) 1155 link disparate base stations 1110.According to an aspect, backhaul link 1153 can connect multiple femtoaccess points 1130 and/or controller components (CC) 1101 to the femtonetwork platform 1102. In one example, multiple femto APs can beconnected to a routing platform (RP) 1087, which in turn can be connectto a controller component (CC) 1101. Typically, the information from UEs1120 _(A) can be routed by the RP 102, for example, internally, toanother UE 1120 _(A) connected to a disparate femto AP connected to theRP 1087, or, externally, to the femto network platform 1102 via the CC1101, as discussed in detail supra.

In wireless environment 1150, within one or more macro cell(s) 1105, aset of femtocells 1145 served by respective femto access points (APs)1130 can be deployed. It can be appreciated that, aspects of the subjectinnovation are geared to femtocell deployments with substantive femto APdensity, e.g., 10 ⁴-10 ⁷ femto APs 1130 per base station 1110. Accordingto an aspect, a set of femto access points 1130 ₁-3730 _(N), with N anatural number, can be functionally connected to a routing platform1087, which can be functionally coupled to a controller component 1101.The controller component 1101 can be operationally linked to the femtonetwork platform 330 by employing backhaul link(s) 1153. Accordingly,UEs UE 3720 _(A) connected to femto APs 1130 ₁-3830 _(N) can communicateinternally within the femto enterprise via the routing platform (RP)1087 and/or can also communicate with the femto network platform 1102via the RP 1087, controller component 1101 and the backhaul link(s)1153. It can be appreciated that although only one femto enterprise isdepicted in FIG. 11, multiple femto enterprise networks can be deployedwithin a macro cell 1105.

It is noted that while various aspects, features, or advantagesdescribed herein have been illustrated through femto access point(s) andassociated femto coverage, such aspects and features also can beexploited for home access point(s) (HAPs) that provide wireless coveragethrough substantially any, or any, disparate telecommunicationtechnologies, such as for example Wi-Fi (wireless fidelity) or picocelltelecommunication. Additionally, aspects, features, or advantages of thesubject innovation can be exploited in substantially any wirelesstelecommunication, or radio, technology; for example, Wi-Fi, WorldwideInteroperability for Microwave Access (WiMAX), Enhanced General PacketRadio Service (Enhanced GPRS), 3GPP LTE, 3GPP2 UMB, 3GPP UMTS, HSPA,HSDPA, HSUPA, or LTE Advanced. Moreover, substantially all aspects ofthe subject innovation can include legacy telecommunicationtechnologies.

Referring now to FIG. 12, there is illustrated a block diagram of anexemplary computer system operable to execute the disclosedarchitecture. In order to provide additional context for various aspectsof the disclosed subject matter, FIG. 12 and the following discussionare intended to provide a brief, general description of a suitablecomputing environment 1200 in which the various aspects of the disclosedsubject matter can be implemented. Additionally, while the disclosedsubject matter described above may be suitable for application in thegeneral context of computer-executable instructions that may run on oneor more computers, those skilled in the art will recognize that thedisclosed subject matter also can be implemented in combination withother program modules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the disclosed subject matter may also bepracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

A computer typically includes a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the computer and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can include eithervolatile or nonvolatile, removable and non-removable media implementedin any method or technology for storage of information such ascomputer-readable instructions, data structures, program modules orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disk (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

With reference again to FIG. 12, the exemplary environment 1200 forimplementing various aspects of the disclosed subject matter includes acomputer 1202, the computer 1202 including a processing unit 1204, asystem memory 1206 and a system bus 1208. The system bus 1208 couples tosystem components including, but not limited to, the system memory 1206to the processing unit 1204. The processing unit 1204 can be any ofvarious commercially available processors. Dual microprocessors andother multi-processor architectures may also be employed as theprocessing unit 1204.

The system bus 1208 can be any of several types of bus structure thatmay further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1206includes read-only memory (ROM) 1210 and random access memory (RAM)1212. A basic input/output system (BIOS) is stored in a non-volatilememory 1210 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1202, such as during start-up. The RAM 1212 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1202 further includes an internal hard disk drive (HDD)1214 (e.g., EIDE, SATA), which internal hard disk drive 1214 may also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1216, (e.g., to read from or write to aremovable diskette 1218) and an optical disk drive 1220, (e.g., readinga CD-ROM disk 1222 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1214, magnetic diskdrive 1216 and optical disk drive 1220 can be connected to the systembus 1208 by a hard disk drive interface 1224, a magnetic disk driveinterface 1226 and an optical drive interface 1228, respectively. Theinterface 1224 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE1394 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject matter disclosed herein.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1202, the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer, such as zipdrives, magnetic cassettes, flash memory cards, cartridges, and thelike, may also be used in the exemplary operating environment, andfurther, that any such media may contain computer-executableinstructions for performing the methods of the disclosed subject matter.

A number of program modules can be stored in the drives and RAM 1212,including an operating system 1230, one or more application programs1232, other program modules 1234 and program data 1236. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1212. It is appreciated that the disclosed subjectmatter can be implemented with various commercially available operatingsystems or combinations of operating systems.

A user can enter commands and information into the computer 1202 throughone or more wired/wireless input devices, e.g., a keyboard 1238 and apointing device, such as a mouse 1240. Other input devices (not shown)may include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1204 through an input deviceinterface 1242 that is coupled to the system bus 1208, but can beconnected by other interfaces, such as a parallel port, an IEEE1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1244 or other type of display device is also connected to thesystem bus 1208 via an interface, such as a video adapter 1246. Inaddition to the monitor 1244, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1202 may operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1248. The remotecomputer(s) 1248 can be a workstation, a server computer, a router, apersonal computer, a mobile device, portable computer,microprocessor-based entertainment appliance, a peer device or othercommon network node, and typically includes many or all of the elementsdescribed relative to the computer 1202, although, for purposes ofbrevity, only a memory/storage device 1250 is illustrated. The logicalconnections depicted include wired/wireless connectivity to a local areanetwork (LAN) 1252 and/or larger networks, e.g., a wide area network(WAN) 1254. Such LAN and WAN networking environments are commonplace inoffices and companies, and facilitate enterprise-wide computer networks,such as intranets, all of which may connect to a global communicationsnetwork, e.g., the Internet.

When used in a LAN networking environment, the computer 1202 isconnected to the local network 1252 through a wired and/or wirelesscommunication network interface or adapter 1256. The adapter 1256 mayfacilitate wired or wireless communication to the LAN 1252, which mayalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1256.

When used in a WAN networking environment, the computer 1202 can includea modem 1258, or is connected to a communications server on the WAN1254, or has other means for establishing communications over the WAN1254, such as by way of the Internet. The modem 1258, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1208 via the serial port interface 1242. In a networkedenvironment, program modules depicted relative to the computer 1202, orportions thereof, can be stored in the remote memory/storage device1250. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers can be used.

The computer 1202 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE802.11 (a, b,g, n, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE802.3 or Ethernet). Wi-Finetworks operate in the unlicensed 2.4 and 5 GHz radio bands, at an 11Mbps (802.11b) or 54 Mbps (802.11a) data rate, for example, or withproducts that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic “10 BaseT” wiredEthernet networks used in many offices.

Various aspects or features described herein can be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques. In addition, various aspects disclosed inthe subject specification can also be implemented through programmodules stored in a memory and executed by a processor, or othercombination of hardware and software, or hardware and firmware. The term“article of manufacture” as used herein is intended to encompass acomputer program accessible from any computer-readable device, carrier,or media. For example, computer readable media can include but are notlimited to magnetic storage devices (e.g., hard disk, floppy disk,magnetic strips . . . ), optical disks (e.g., compact disc (CD), digitalversatile disc (DVD), blu-ray disc (BD) . . . ), smart cards, and flashmemory devices (e.g., card, stick, key drive . . . ). Additionally itshould be appreciated that a carrier wave can be employed to carrycomputer-readable electronic data such as those used in transmitting andreceiving electronic mail or in accessing a network such as the internetor a local area network (LAN). Of course, those skilled in the art willrecognize many modifications may be made to this configuration withoutdeparting from the scope or spirit of the disclosed subject matter.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor also can be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “data store,” “datastorage,” “database,” “repository,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory. In addition, memory components or memory elementscan be removable or stationary. Moreover, memory can be internal orexternal to a device or component, or removable or stationary. Memorycan include various types of media that are readable by a computer, suchas hard-disc drives, zip drives, magnetic cassettes, flash memory cardsor other types of memory cards, cartridges, or the like.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

What has been described above includes examples of the variousembodiments. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the embodiments, but one of ordinary skill in the art mayrecognize that many further combinations and permutations are possible.Accordingly, the detailed description is intended to embrace all suchalterations, modifications, and variations that fall within the spiritand scope of the appended claims.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms (including a reference to a “means”) used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., a functional equivalent), even though not structurallyequivalent to the disclosed structure, which performs the function inthe herein illustrated exemplary aspects of the embodiments. In thisregard, it will also be recognized that the embodiments includes asystem as well as a computer-readable medium having computer-executableinstructions for performing the acts and/or events of the variousmethods.

In addition, while a particular feature may have been disclosed withrespect to only one of several implementations, such feature may becombined with one or more other features of the other implementations asmay be desired and advantageous for any given or particular application.Furthermore, to the extent that the terms “includes,” and “including”and variants thereof are used in either the detailed description or theclaims, these terms are intended to be inclusive in a manner similar tothe term “comprising.”

1. A system that facilitates automatic or dynamic detection or remedy ofservice usage inequities in a communications network, comprising: anextraction component that retrieves subscriber information associatedwith a subscriber to a communications network, wherein the subscriberinformation includes at least a call detail record (CDR) associated witha communication transaction of the subscriber; and a detection componentthat examines the subscriber information and that generates a data usageevent message when a usage inequity is identified.
 2. The system ofclaim 1, the extraction component retrieves the CDR from a GeneralPacket Radio Service (GPRS) Serving Support Node (SGSN) associated withthe communications network.
 3. The system of claim 1, the subscriberinformation further comprises rules data or provision data that includesdata relating to at least one of a provisioned service agreement agreedto by the subscriber, enabled features associated with the serviceagreement, terms and conditions associated with the service agreement,other available service plans.
 4. The system of claim 3, the extractioncomponent retrieves the provision data from an accounts data storeassociated with the communications network.
 5. The system of claim 1,the usage inequity relates to avoidable high data usage charges deemedlikely to arise during a billing cycle or otherwise, or to usage that ismore suitable for a disparate service agreement or features thereof. 6.The system of claim 5, the detection component identifies the avoidablehigh data usage charges by forecasting usage relative to time remainingin a billing cycle or by identifying usage that surpasses a respectivethreshold at one or more periods of a billing cycle.
 7. The system ofclaim 1, the usage inequity relates to a usage violation in which usageof the communications network violates a provisioned service agreementagreed to by the subscriber.
 8. The system of claim 7, the detectioncomponent, in order to identify the usage violation, converts anInternational Mobile Equipment Identity (IMEI) included in the CDR intoan IMEI type that identifies a type or class of equipment employed forthe communication transaction.
 9. The system of claim 8, the detectioncomponent, in order to identify the usage violation, compares the IMEItype to allowable equipment included in the subscriber information or toa blacklist equipment list based upon the subscriber information. 10.The system of claim 1, the usage inequity is at least one of aSubscriber Information Module (SIM) swap to an unauthorized orblacklisted device or a communication-based device tethering of userequipment to an unauthorized or blacklisted device.
 11. The system ofclaim 1, the usage inequity is identified substantially in real time.12. The system of claim 1, further comprising at least one of: a controlservice component that receives the data usage event message and thatdetermines, based upon rules data, a suitable treatment to apply inconnection with the subscriber; or an interface component that enablesauthorized administrators to create or update the rules data.
 13. Thesystem of claim 12, the suitable treatment includes at least one of (1)a notification to the subscriber, wherein the notification includes oneor more of the usage inequity, suggested remedies, potential actionsshould the usage inequity continue, or further contact information; (2)facilitate additional or more detailed monitoring of data usagesassociated with the subscriber; (3) a restriction to data usage orservices associated with the subscriber; or (4) a termination of datausage or services associated with the subscriber.
 14. The system ofclaim 13, the control service component facilitates transmission of thenotification to the subscriber by way of short message service (SMS),email, or mail.
 15. The system of claim 14, the control servicecomponent automatically facilitates an update to a provisioned serviceagreement or associated features when the subscriber authorizes theupdate or requests an exemption in response to the notification.
 16. Thesystem of claim 12, the control service component does not applytreatment during a provisional period for a newly created or updatedrule in which the service component instead facilitates an audit trailto measure the effects of treatment defined by the newly created orupdated rule.
 17. A method for automatically or dynamically detecting orremedying service usage inequities for a communications network,comprising: receive at least one call detail record (CDR) associatedwith at least one communication transaction of at least one subscriberto the communications network; obtaining additional subscriberinformation relating to service agreements or to features, options,terms, conditions, or rules data related thereto; comparing CDR data tothe additional subscriber information for determining an usage inequity;and outputting a data usage event message describing the usage inequity.18. The method of claim 17, further comprising at least one of thefollowing acts: determining the usage inequity when avoidable high datausage charges are inferred to arise during a current billing cycle;determining the usage inequity when usage of the communication networkviolates a provisioned service agreement agreed to by the at least onesubscriber; translating an International Mobile Equipment Identifier(IMEI) included in the at least one CDR to an IMEI type that indicates atype or class of equipment employed for the at least one communicationtransaction associated with the at least one CDR; comparing the IMEItype to allowable equipment included in the additional subscriberinformation or to a blacklist equipment list particular to a serviceagreement associated with the at least one subscriber; utilizing theIMEI or the IMEI type for detecting an unauthorized subscriberinformation module (SIM) swap or an unauthorized communication-baseddevice tethering; or outputting the data usage event messagesubstantially in real time.
 19. The method of claim 17, furthercomprising at least one of the following acts: providing an interfacefor enabling authorized administrators to create or update the rulesdata; determining a treatment to apply based upon the data usage eventmessage and the rules data; propagating a notification associated withthe treatment to the subscriber by way of at least one of short messageservice (SMS), email, or mail; automatically facilitating an update to aprovisioned service or an agreement thereof or associated features whenthe at least one subscriber authorizes the update or requests anexemption in response to the notification; foregoing application of thetreatment during a provisional period for a newly created or newlyupdated rule; or generating an audit trail for measuring effects oftreatment defined by the newly created or newly updated rule during theprovisional period.
 20. A system that facilitates automatic or dynamicdetection or remedy of service usage inequities in a communicationsnetwork, comprising: an extraction component that retrieves subscriberinformation associated with a subscriber to a communications network,wherein the subscriber information includes at least a call detailrecord (CDR) associated with a communication transaction of thesubscriber; a detection component that examines the subscriberinformation and that generates a data usage event message when a usageinequity is identified; and a control service component that receivesthe data usage event message and that determines, based upon rules data,a suitable treatment to apply in connection with the subscriber.